ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Topics
    2. Tags
    3. ntg lab
    Log in to post
    • All categories
    • scottalanmillerS

      Testing UbuntuBSD on the Scale HC3

      IT Discussion
      • scale scale hc3 freebsd ubuntu ubuntubsd ubuntu 15.10 ntg lab unix • • scottalanmiller
      1
      5
      Votes
      1
      Posts
      1.8k
      Views

      No one has replied

    • scottalanmillerS

      Installing GitLab on CentOS 7

      IT Discussion
      • ntg lab scale scale hc3 gitlab open source centos centos 7 linux how to rhel 7 rhel • • scottalanmiller
      13
      4
      Votes
      13
      Posts
      3.7k
      Views

      scottalanmillerS

      @dafyre said:

      @JaredBusch said:

      @dafyre said:

      As a matter of correctness... Do you have EPEL /REMI or any other repos installed in your CentOS 7 image?

      The script is connecting the Gitlab RPM, that is all. The base image he uses for all of these is CentOS 7 minimal, release 1511 unless he has changed the base template on his scale cluster.

      Right. I'm just curious if he has added the epel-release or any other repos to it.

      Definitely no EPEL. I often use it, but avoid it in the base image.

    • scottalanmillerS

      Installing ownCloud 9 on CentOS 7

      IT Discussion
      • owncloud owncloud 9 storage open source centos centos 7 linux linux server ntg lab scale scale hc3 • • scottalanmiller
      116
      3
      Votes
      116
      Posts
      39.9k
      Views

      JaredBuschJ

      @wirestyle22 said:

      @coliver said:

      @wirestyle22 said:

      I have to look up SSL certification on CentOS 7 now. I've only ever done it on our Barracuda SSL VPN which was just an upload. Here we go

      I think you need to look up SSL for Apache if you are trying to encrypt ownCloud. I think someone has a guide on here somewhere about it.

      I think @JaredBusch has it in his 8.2 guide. I think he did self signed though. I'm unsure of how to do this on linux with digicert or something similar

      It was a self signed for the example. but I use letsencrypt myself. Some clients using ownCloud have StartSSL certs.

    • scottalanmillerS

      Installing Zimbra Email 8.6 on CentOS 7

      IT Discussion
      • ntg lab scale scale hc3 email centos centos 7 how to linux zimbra zcs open source zimbra 8.6 rhel 7 • • scottalanmiller
      43
      6
      Votes
      43
      Posts
      13.5k
      Views

      dbeatoD

      @travisdh1 said in Installing Zimbra Email 8.6 on CentOS 7:

      @scottalanmiller said in Installing Zimbra Email 8.6 on CentOS 7:

      8.8.9 is out now...

      https://files.zimbra.com/downloads/8.8.9_GA/zcs-NETWORK-8.8.9_GA_2055.RHEL7_64.20180703080917.tgz

      8.8.10 is now out
      https://files.zimbra.com/downloads/8.8.10_GA/zcs-8.8.10_GA_3039.RHEL6_64.20180928094617.tgz

      There is also a patch for 8.8.10 as well
      https://blog.zimbra.com/2018/10/new-zimbra-patches-8-8-10-patch-1-and-8-8-9-patch-6/

    • scottalanmillerS

      Configuring LogStash and FileBeat to Send to ELK Logging System

      IT Discussion
      • logstash filebeat elk log management logging ntg lab • • scottalanmiller
      11
      4
      Votes
      11
      Posts
      6.7k
      Views

      DustinB3403D

      For anyone looking to do this here is my filebeat.yml file.

      # Name of the registry file. Per default it is put in the current working # directory. In case the working directory is changed after when running # filebeat again, indexing starts from the beginning again. registry_file: /var/lib/filebeat/registry # Full Path to directory with additional prospector configuration files. Each file must end with .yml # These config files must have the full filebeat config part inside, but only # the prospector part is processed. All global options like spool_size are ignored. # The config_dir MUST point to a different directory then where the main filebeat config file is in. #config_dir: ############################################################################### ############################# Libbeat Config ################################## # Base config file used by all other beats for using libbeat features ############################# Output ########################################## # Configure what outputs to use when sending the data collected by the beat. # Multiple outputs may be used. output: ### Elasticsearch as output elasticsearch: # Array of hosts to connect to. # Scheme and port can be left out and will be set to the default (http and 9200) # In case you specify and additional path, the scheme is required: http://localhost:9200/path # IPv6 addresses should always be defined as: https://[2001:db8::1]:9200 hosts: ["localhost:9200"] # Optional protocol and basic auth credentials. #protocol: "https" #username: "admin" #password: "s3cr3t" # Number of workers per Elasticsearch host. #worker: 1 # Optional index name. The default is "filebeat" and generates # [filebeat-]YYYY.MM.DD keys. #index: "filebeat" # A template is used to set the mapping in Elasticsearch # By default template loading is disabled and no template is loaded. # These settings can be adjusted to load your own template or overwrite existing ones #template: # Template name. By default the template name is filebeat. #name: "filebeat" # Path to template file #path: "filebeat.template.json" # Overwrite existing template #overwrite: false # Optional HTTP Path #path: "/elasticsearch" # Proxy server url #proxy_url: http://proxy:3128 # The number of times a particular Elasticsearch index operation is attempted. If # the indexing operation doesn't succeed after this many retries, the events are # dropped. The default is 3. #max_retries: 3 # The maximum number of events to bulk in a single Elasticsearch bulk API index request. # The default is 50. #bulk_max_size: 50 # Configure http request timeout before failing an request to Elasticsearch. #timeout: 90 # The number of seconds to wait for new events between two bulk API index requests. # If `bulk_max_size` is reached before this interval expires, addition bulk index # requests are made. #flush_interval: 1 # Boolean that sets if the topology is kept in Elasticsearch. The default is # false. This option makes sense only for Packetbeat. #save_topology: false # The time to live in seconds for the topology information that is stored in # Elasticsearch. The default is 15 seconds. #topology_expire: 15 # tls configuration. By default is off. #tls: # List of root certificates for HTTPS server verifications certificate_authorities: ["/etc/pki/tls/certs/logstash-forwarder.crt"] # Certificate for TLS client authentication #certificate: "/etc/pki/client/cert.pem" # Client Certificate Key #certificate_key: "/etc/pki/client/cert.key" # Controls whether the client verifies server certificates and host name. # If insecure is set to true, all server host names and certificates will be # accepted. In this mode TLS based connections are susceptible to # man-in-the-middle attacks. Use only for testing. #insecure: true # Configure cipher suites to be used for TLS connections #cipher_suites: [] # Configure curve types for ECDHE based cipher suites #curve_types: [] # Configure minimum TLS version allowed for connection to logstash #min_version: 1.0 # Configure maximum TLS version allowed for connection to logstash #max_version: 1.2 ### Logstash as output #logstash: # The Logstash hosts hosts: ["localhost:5044"] # Number of workers per Logstash host. #worker: 1 # Set gzip compression level. #compression_level: 3 # Optional load balance the events between the Logstash hosts #loadbalance: true # Optional index name. The default index name depends on the each beat. # For Packetbeat, the default is set to packetbeat, for Topbeat # top topbeat and for Filebeat to filebeat. #index: filebeat # Optional TLS. By default is off. #tls: # List of root certificates for HTTPS server verifications #certificate_authorities: ["/etc/pki/root/ca.pem"] # Certificate for TLS client authentication #certificate: "/etc/pki/client/cert.pem" # Client Certificate Key #certificate_key: "/etc/pki/client/cert.key" # Controls whether the client verifies server certificates and host name. # If insecure is set to true, all server host names and certificates will be # accepted. In this mode TLS based connections are susceptible to # man-in-the-middle attacks. Use only for testing. #insecure: true # Configure cipher suites to be used for TLS connections #cipher_suites: [] # Configure curve types for ECDHE based cipher suites #curve_types: [] ### File as output #file: # Path to the directory where to save the generated files. The option is mandatory. #path: "/tmp/filebeat" # Name of the generated files. The default is `filebeat` and it generates files: `filebeat`, `filebeat.1`, `filebeat.2`, etc. #filename: filebeat # Maximum size in kilobytes of each file. When this size is reached, the files are # rotated. The default value is 10 MB. #rotate_every_kb: 10000 # Maximum number of files under path. When this number of files is reached, the # oldest file is deleted and the rest are shifted from last to first. The default # is 7 files. #number_of_files: 7 ### Console output # console: # Pretty print json event #pretty: false ############################# Shipper ######################################### shipper: # The name of the shipper that publishes the network data. It can be used to group # all the transactions sent by a single shipper in the web interface. # If this options is not defined, the hostname is used. #name: # The tags of the shipper are included in their own field with each # transaction published. Tags make it easy to group servers by different # logical properties. #tags: ["service-X", "web-tier"] # Uncomment the following if you want to ignore transactions created # by the server on which the shipper is installed. This option is useful # to remove duplicates if shippers are installed on multiple servers. #ignore_outgoing: true # How often (in seconds) shippers are publishing their IPs to the topology map. # The default is 10 seconds. #refresh_topology_freq: 10 # Expiration time (in seconds) of the IPs published by a shipper to the topology map. # All the IPs will be deleted afterwards. Note, that the value must be higher than # refresh_topology_freq. The default is 15 seconds. #topology_expire: 15 # Internal queue size for single events in processing pipeline #queue_size: 1000 # Configure local GeoIP database support. # If no paths are not configured geoip is disabled. #geoip: #paths: # - "/usr/share/GeoIP/GeoLiteCity.dat" # - "/usr/local/var/GeoIP/GeoLiteCity.dat" ############################# Logging ######################################### # There are three options for the log ouput: syslog, file, stderr. # Under Windos systems, the log files are per default sent to the file output, # under all other system per default to syslog. logging: # Send all logging output to syslog. On Windows default is false, otherwise # default is true. #to_syslog: true # Write all logging output to files. Beats automatically rotate files if rotateeverybytes # limit is reached. #to_files: false # To enable logging to files, to_files option has to be set to true files: # The directory where the log files will written to. #path: /var/log/mybeat # The name of the files where the logs are written to. #name: mybeat # Configure log file size limit. If limit is reached, log file will be # automatically rotated rotateeverybytes: 10485760 # = 10MB # Number of rotated log files to keep. Oldest files will be deleted first. #keepfiles: 7 # Enable debug output for selected components. To enable all selectors use ["*"] # Other available selectors are beat, publish, service # Multiple selectors can be chained. #selectors: [ ] # Sets log level. The default log level is error. # Available log levels are: critical, error, warning, info, debug #level: error
    • scottalanmillerS

      Building ELK on CentOS 7

      IT Discussion
      • scale ntg lab scale hc3 centos centos 7 elk logging log management how to linux elasticsearch kibana logstash kibana 4 • • scottalanmiller
      43
      9
      Votes
      43
      Posts
      16.2k
      Views

      dafyreD

      @scottalanmiller said in Building ELK on CentOS 7:

      @dafyre said in Building ELK on CentOS 7:

      So... I went through and ran the script and it seems to have worked fine... What next?

      Edit: To collect logs from the local server, I also had to install filebeat on this server. So I reckon I can now go and install it on all my other systems as well.

      Yes, install Filebeat and point it to ELK. Check my Filebeat article for more info.

      Didn't realize you had one. 8-) But I'm good now. Logs are collecting as we speak. Bonus: Fail2Ban and Apache logs also work great in ELK.

    • scottalanmillerS

      Installing Rocket.Chat on CentOS 7

      IT Discussion
      • rocketchat instant messaging centos 7 centos rhel 7 linux linux server ntg lab scale scale hc3 • • scottalanmiller
      30
      7
      Votes
      30
      Posts
      12.9k
      Views

      scottalanmillerS

      @ou_snaaksie said in Installing Rocket.Chat on CentOS 7:

      The installation worked perfetly, but after restarting the server I am unable to access Rocketchat.

      I've run the line:
      /opt/Rocket.Chat/node_modules/forever/bin/forever start /opt/Rocket.Chat/main.js

      but it is still not working.

      Use this command to see what is listening...

      netstat -tulpn
    • scottalanmillerS

      Installing MongoDB 3.2 on CentOS 7

      IT Discussion
      • ntg lab scale scale hc3 mongodb mongodb 3 mongodb 3.2 nosql centos linux server linux centos 7 rhel 7 • • scottalanmiller
      7
      5
      Votes
      7
      Posts
      5.0k
      Views

      JaredBuschJ

      @scottalanmiller said in Installing MongoDB 3.2 on CentOS 7:

      Just tested and deployed to CentOS 7.2 on Linode.

      This failed me, so I went to the mongo docs and the baseurl contains the variable $releasever.

      using that results in redhat//mongodb in the file, which is why I assume you hard coded that bit.

      Escaping the $ fixes it.

      cat > /etc/yum.repos.d/mongodb-org-3.2.repo <<EOF [mongodb-org-3.2] name=MongoDB Repository baseurl=https://repo.mongodb.org/yum/redhat/\$releasever/mongodb-org/3.2/x86_64/ gpgcheck=1 enabled=1 gpgkey=https://www.mongodb.org/static/pgp/server-3.2.asc EOF
    • scottalanmillerS

      Adding ZeroTier to the NTG Lab

      IT Discussion
      • ntg lab zerotier vpn • • scottalanmiller
      3
      7
      Votes
      3
      Posts
      1.9k
      Views

      scottalanmillerS

      This will be good for things like the Rocket.Chat system too. Was thinking that we would get that up and running in the lab for communication between people working in the lab so that they could coordinate easily. Although perhaps just an IRC channel would make more sense for that. But delivering those kinds of things over ZeroTier is easy.

    • antonitA

      Installing MariaDB

      IT Discussion
      • mariadb database zabbix centos centos 7 linux ntg lab • • antonit
      8
      1
      Votes
      8
      Posts
      1.9k
      Views

      scottalanmillerS

      @antonit said:

      What is the default db admin?

      root

    • scottalanmillerS

      Installing Our First Linux Virtual Machine for Learning Systems Administration

      IT Careers
      • linux centos centos 7 system administration career scale virtualization scale hc3 rhel rhel 7 ntg lab sam linux administration • • scottalanmiller
      32
      13
      Votes
      32
      Posts
      10.8k
      Views

      NerdyDadN

      Had a spare laptop laying around. Installing CentOS now. Also planning on installing NextCloud here soon as well. Creating a repository/shared calendar for the family with this machine.

    • scottalanmillerS

      Building Stacki 3 Provisioning Server Frontend on the Scale HC3 Cluster in the NTG Lab

      IT Discussion
      • stacki stacki 3 centos centos 7 linux devops scale scale hc3 ntg lab linux server projects open source • • scottalanmiller
      8
      2
      Votes
      8
      Posts
      2.7k
      Views

      scottalanmillerS

      Updated as I figured out where things have moved away from the documentation that I had. The five minute install video is for Stacki 1.x and they have changed quite a bit at the core so that is why the video does not reflect the needs of the current installer. Avoid the StackiQ video for installation.

    • scottalanmillerS

      Getting Deepin 2015 Installed on a Scale HC3 Cluster

      IT Discussion
      • ntg lab linux linux desktop deepin deeping 2015 scale scale hc3 screenshots • • scottalanmiller
      6
      4
      Votes
      6
      Posts
      2.4k
      Views

      scottalanmillerS

      @Dashrender said:

      I know China was working on a version many years ago - wasn't sure if this was related.

      That's Red Flag Linux, they have been using that for around a decade.

    • scottalanmillerS

      Mounting an NFS Home Share on CentOS 7 Clients

      IT Discussion
      • nfs nfs 3 centos centos 7 file server home ntg lab scale scale hc3 rhel rhel 7 linux • • scottalanmiller
      13
      9
      Votes
      13
      Posts
      9.1k
      Views

      scottalanmillerS

      No, there is nothing like that. The filesystem is just not there. It would warn you, though, so you would know not to be trying to save to something that doesn't exist.

    • scottalanmillerS

      Building an NFS Home Directory Server for the NTG Lab

      IT Discussion
      • scale scale hc3 ntg lab opensuse leap nfs nfs 3 storage file server server linux linux server suse nas • • scottalanmiller
      33
      5
      Votes
      33
      Posts
      9.4k
      Views

      scottalanmillerS

      It is not uncommon to only have servers approved to access the storage listed. So many shops will go in and add a server one by one to enable access. If your servers almost never change, this works pretty well and is extremely secure. You can do this in the firewall too, for even more security. But if you are using DevOps and creating and destroying VMs regularly you will want to automate this in some fashion.

    • scottalanmillerS

      Installing MineCraft Server on CentOS 7 with Oracle Java 8

      IT Discussion
      • java minecraft linux linux server gaming scale scale hc3 centos centos 7 virtualization ntg lab • • scottalanmiller
      9
      6
      Votes
      9
      Posts
      6.6k
      Views

      scottalanmillerS

      Original post has been updated to reflect the latest 0.9 release of the Minecraft Server.

    • scottalanmillerS

      Installing PocketMine MineCraft PE Server on CentOS 7

      IT Discussion
      • scale scale hc3 pocketmine minecraft minecraft pe gaming linux linux server centos centos 7 php open source ntg lab • • scottalanmiller
      143
      6
      Votes
      143
      Posts
      69.6k
      Views

      scottalanmillerS

      @clisting said in Installing PocketMine MineCraft PE Server on CentOS 7:

      it constantly disconnects me. the server appears to be online please help me.

      I've not touched this in three and a half years, I'm afraid. This stuff easily doesn't work any longer 😞

    • scottalanmillerS

      Windows Server 2016 TP4 on Scale HC3 HC2000 Test

      IT Discussion
      • scale hc3 windows server 2016 ntg lab windows server • • scottalanmiller
      26
      9
      Votes
      26
      Posts
      4.5k
      Views

      DashrenderD

      @JaredBusch said:

      @BRRABill said:

      @scottalanmiller said:

      Apparently, when have they NOT? Where does this "first release" myth come from? Other than the unique case of Vista, which was a true first release of NT 6. This is NOT a first release, this is the latest version of NT 6. If you have concern about lower releases, then that would make you install this as this is the latest update to NT 6.

      On the desktop side, I typically have always felt the first releases (like the now defunct Windows 😎 to be shaky. I do not think that is a myth.

      There was not a single functionality issue with Windows 8.
      Honestly, there was not a single problem with Vista either as long as your hardware worked with it. Vista had a driver compatibility problem.

      Well this is not entirely true. Vista also included a brand new network stack that they wrote that had TONS of holes in it. They dumped that stack with 8.1 though.

    • scottalanmillerS

      OpenSuse Leap 42.1 Text Install on Scale HC3

      IT Discussion
      • scale scale hc3 ntg lab opensuse suse opensuse leap 42.1 linux screenshots • • scottalanmiller
      1
      5
      Votes
      1
      Posts
      2.1k
      Views

      No one has replied

    • scottalanmillerS

      Our New Scale Cluster Arrives Tomorrow

      IT Discussion
      • scale ntg lab hyperconvergence virtualization kvm scale hc3 scale hc3 hc2000 • • scottalanmiller
      131
      12
      Votes
      131
      Posts
      35.7k
      Views

      scottalanmillerS

      Just updated the cluster to 7.1

    • 1
    • 2
    • 3
    • 2 / 3